Salam, I have successfully installed Exchange 2010 SP1 on a transitional environment, the installation went smooth without any problem and I've done most of the trasitioning configuration from Exchange Server 2003 to Exchange Server 2010. Currently we're in the process of moving the mailboxes, but I've come across a problem recently which stopped all my work and I can no longer commence with this transition unless its solved. Sometimes when I try to access EMC or EMS I get the hereunder error: The following error occurred while attempting to connect to the specified Exchange server 'afhmail.arabfinancehouse.com.lb': The attempt to connect to http://afhmail.arabfinancehouse.com.lb/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic. I've read most of the articles found on the internet including http://msexchangeteam.com/archive/2010/02/04/453946.aspx to try to troubleshoot this problem but nothing has worked so far, I tried removing Win RM IIS extensions as well then adding them again with a restart and nothing. I tried the Kerbauth dll removal also nothing and the problem keeps to occur and the situation is not stable. Also I read in a KB article somewhere that if we have multiple domain controllers a single domain controller should be assigned on the Exchange Server (Organization Configuration, Server Configuration, Recipient Configuration) so I assigned the PDC to be selected by those configurations at startup, yet I am still facing the same problem. Again I emphasis that the problem comes and goes, at a time I can access EMS and at another is just gives me the Kerberos error. Thank you very much in advance, Kindest Regards.Abdullah Abdullah

Hi, Hope this link might help you. http://blogs.technet.com/b/richardroddy/archive/2010/10/06/even-more-exchange-2010-management-tools-fun.aspx ThanksNagaraj N

ok you can take help of the troubleshooter discussed in this blog http://msexchangeteam.com/archive/2010/12/07/457139.aspx by the way looks like the error message you got does not match the cases discussed in the blog http://msexchangeteam.com/archive/2010/02/04/453946.aspx. Dhruv

Salam, Thank you Dhruvaraj, but I've used the troubleshooter as well with no luck. Currently I'm moving all mailboxes back to 2k3 and I'll do some more troubleshooting then. Thank you.Abdullah Abdullah

Hi Abdullah, Can you open the EMS? If yes, please run the WinRM QC and post the results here. If possible, please use another admin's account to log on to Exchange to try to open EMC. Frank Wang TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Abdullah, Any updates on your issue?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I get the same error. Noone seems to have a solution...?!

Hello. Please make sure that the WWW Publishing Service is started. Cheers.Miguel Fra | Falcon IT Services, Miami, FL www.falconitservices.com | www.falconits.com | Blog

Salam, Sorry for the delay in replying to all, but the problem seemed to be in time synchronization. I noticed that the time differed from that of the MDC even though I tried troubleshooting it much nothing had worked so I removed everything and started from scratch. I believe now in Win2k8 R2 SP1 this problem is resolved, thank you all.Abdullah^2

This issue occurs because you need to fix the bindings on 'Default Web Site' in IIS Mananger... Make sure it contains these bindings: Type port ip address binding information net.tcp 808:* net.pipe * net.msmq localhost msmq.formatname localhost http 80 127.0.0.1 https 443 * http 80 * https 443 127.0.0.1 ... it worked for me. I had removed http 80 * to harded IIS when this issue started. I put it back in and it worked again.